-
Notifications
You must be signed in to change notification settings - Fork 109
Puf/cloud functions testing #313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Add description of testing push notifications without writing to Firestore (by using the testing functionality built into the Google Cloud console).
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added few small suggestions! You can batch commit the suggestions from the Files Changed View. Otherwise LGTM! Thank you so much!
Add back block quote
…terFlow/flutterflow-documentation into puf/cloud-functions-testing
@@ -245,6 +245,44 @@ For this example, we'll use the result (i.e., generated logo image URL) and set | |||
<div class="video-container"><iframe src="https://www.loom. | |||
com/embed/0c4306c1951a4d9099aa96324c7561af?sid=69709110-ad60-4e98-bf53-36a50a99e425" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div> | |||
|
|||
## Testing Cloud Functions by sending push notifications without writing to Firestore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is a very long heading! I meant to keep just "Testing Cloud Functions" because its relevant to all Functions, using PNs as an example thoughn
Hence my having a subheading in there. :)
I'm OK with dropping the "without writing to Firestore", but want to keep
the "by sending push notifications" in the heading as I expect that to SEO
well, which is necessary since this is *not* in the docs section on push
notifications.
…On Fri, Apr 4, 2025 at 10:44 AM Pooja Bhaumik ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In docs/ff-concepts/adding-customization/cloud-functions.md
<#313 (comment)>
:
> @@ -245,6 +245,44 @@ For this example, we'll use the result (i.e., generated logo image URL) and set
<div class="video-container"><iframe src="https://www.loom.
com/embed/0c4306c1951a4d9099aa96324c7561af?sid=69709110-ad60-4e98-bf53-36a50a99e425" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
+## Testing Cloud Functions by sending push notifications without writing to Firestore
That is a very long heading! I meant to keep just "Testing Cloud
Functions" because its relevant to all Functions, using PNs as an example
thoughn
—
Reply to this email directly, view it on GitHub
<#313 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG7BX7NX5QTA5URRG7NPMD2X3AGBAVCNFSM6AAAAAB2NE734KVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDONBTG4ZTEOJUGE>
.
You are receiving this because you modified the open/close state.Message
ID: <FlutterFlow/flutterflow-documentation/pull/313/review/2743732941@
github.com>
|
Yes for that, I will add a link to this section from push notifications page and there we can use the full heading and point it to this section. But in cloud functions section, generic testing information may be better. I'll add a separate ticket for adding link from push notifications page. |
How to test the Cloud Function to send push notification without writing to Firestore
Describe how to test the Cloud Function to send push notification without writing to Firestore, by using the built-in functionality of the Google Cloud console.
Linear ticket and magic word Fixes DEVR-865
Type of change